Systems and methods for rapidly provisioning functionality to one or more mobile communication devices

ABSTRACT

Systems and methods for rapidly provisioning functionality to one or more mobile communication devices are disclosed. The method may comprise generating, prior to a request for the functionality, a globally unique identifier (“GUID”) encryption key, wherein the GUID comprises a unique identifier that may be associated with a transaction account customer, generating a value associated with the GUID, deriving, based on the value, a plurality of base encryption keys associated with the value, creating, a perso-script, wherein the perso-script comprises a file associated with data associated with a customer, and/or creating a proto-script, wherein the proto-script comprises the perso-script prepended by a script to rotate the plurality of base encryption keys.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a nonprovisional of, claims priority to and thebenefit of, U.S. Ser. No. 61/909,220 filed on Nov. 26, 2013 and entitled“SYSTEMS AND METHODS FOR RAPIDLY PROVISIONING CONTACTLESS PAYMENTFUNCTIONALITY TO ONE OR MORE MOBILE COMMUNICATION DEVICES,” which isincorporated by reference herein in its entirety.

FIELD

The present disclosure generally relates to systems and methods forrapidly provisioning functionality to one or more mobile communicationdevices.

BACKGROUND

Mobile communication devices may facilitate application functionality,such as payment over a wireless communication network. For instance, amobile communication device (e.g., cellular telephone, mobile telephone,a smart phone) may include software and/or hardware that supports orenables wireless communication (e.g., near field communication or “NFC”)by the device with one or more wirelessly enabled point of saleterminals (POS terminals).

Conventionally, a backend system (e.g., a trusted service manager or“TSM”) itself comprising hardware and/or software, may enable anapplication service provider (e.g., American Express) to distribute itsapplication functionality, such as contactless payment software (andfunctionality, as described herein), over a proprietarytelecommunications network (or “Telco”) to a microcontroller (e.g., aUniversal Integrated Circuit Card (“UICC”) or microSD card) locatedwithin the mobile communication device. This integrated circuit may bemore generally referred to as a “secure element” to denote, for example,that the circuit may store an encryption key and/or a set of encryptionkeys used to authenticate the mobile device to a Telco and/or anapplication service provider using the over the air (OTA) Telcoservices.

GlobalPlatform (GP) is the industry standard for securely communicatingwith Secure Elements during manufacturing (i.e., pre-issuance) and whilethe Secure Elements are in the mobile devices held by consumers (i.e.,post-issuance). Additionally, GP provides security controls to protectthe sensitive data and cryptographic keys held in the Secure Element.

GP offers a range of cryptographic key management methods to enable theissuer of the Secure Element, such as a Telco, and the associatedService Providers. These include both “push” and “pull” models. Anexample of the push model is where an application service provider mayrequest that a particular Telco provide (or provision) a cryptographickey or keys (e.g., a symmetric key or keys) to a particular secureelement in response, for example, to a request by the user of the mobilecommunication device for certain contactless payment software and/orfunctionality. In response, the Telco may follow GP to generate (e.g.,randomly generate) and provide the key(s) to the secure element on themobile communication device. The secure element may store the key(s).The Telco may also securely provide a copy of the key to the applicationservice provider. Thus, the secure element and the application serviceprovider may share the key(s); that is, each entity may share this keyas a “shared secret.” The mobile communication device may, in responseto receipt of the shared secret, authenticate to the application serviceprovider to receive the contactless payment software and/orfunctionality.

One aspect of GP is to have robust cryptographic key management. Hence,as part of this “push” process, it is conventionally necessary that theapplication service provider establish (or “rotate” to) a differentcryptographic key(s), so that the Telco (which provided the originalcryptographic key(s) to both the application service provider as well asto the secure element on the mobile device) is no longer able to decryptcommunications between the application service provider and the mobiledevice. However, rotated keys are encrypted and provided to the secureelement, under the key(s) provided by the Telco. Although a secureelement may obtain rotated keys (that is, keys unknown to the Telco), itis conventionally possible for the Telco to decrypt the data packetcontaining the rotated keys during transmission to the secure element,because that packet is encrypted with the key(s) provided during theinitial authentication stage by the Telco.

As the application service provider rotates to a new key set, it is alsoconventionally necessary that the application service provider collectand assemble the data necessary to enable its contactless paymentfunctionality. This functionality may comprise the data necessary tocomplete a contactless payment transaction (e.g., a customer accountnumber, a customer account payment limit, and the like). This collectionof data may be referred to herein as “perso-data,” which may becollected into a file, which may be referred to herein as a“perso-script.” The perso-script may be generated in response to arequest for such functionality and encrypted under session keys based onthe rotated key(s). Hence, the perso-script may itself be at risk ofdecryption by the Telco.

GP also provides for a “pull” model, whereby the Secure Elementgenerates a set of cryptographic keys and securely returns them to theService Provider. This approach typically involves the use of public keycryptography and resolves the vulnerability of the Telco being able toexpose the cryptographic keys (shared between the Secure Element and theService Provider) or the sensitive data protected by those keys.However, even in the “pull” model the Service Provider may well want torotate the keys held in the Secure Element so as to streamlinecryptographic key management on the Service Provider's back end systems,e.g., deriving the keys held on the Secure Element from one or moremaster keys using Secure Element specific information.

A common challenge that both the “pull” and “push” methods face is thatit is typically necessary that the application service provider generatethe perso-script (including the rotated key(s) in response to receipt ofa real-time request for contactless payment functionality. This meansthat the application service provider may have to maintain significantdata processing resources to accommodate millions or tens of millions ofrequests occurring in real-time for contactless payment functionality.This may impose a significant burden on the processing resources (e.g.,hardware) required to generate and encrypt each perso-script, and may infact require that an application service provider maintain a largenumber of such data processing resources (including hardware securitymodules or “HSMs”).

SUMMARY

Systems and methods for rapidly provisioning functionality to one ormore mobile communication devices are disclosed. The method may comprisegenerating, prior to a request for the functionality, a globally uniqueidentifier (“GUID”) master encryption key, wherein the GUID comprises aunique identifier that may be associated with a transaction accountcustomer, generating GUID values, deriving, based on the GUID value, aplurality of base encryption keys associated with the GUID value,creating, a perso-script, wherein the perso-script comprises a fileassociated with data associated with a customer, and/or creating aproto-script, wherein the perso-script comprises the proto-scriptprepended by a script to rotate the plurality of base encryption keys.

The base encryption keys may comprise ENC, MAC and DEK base keys. Thefunctionality may comprise contactless payment functionality. Theperso-data may comprise an alias account number, and/or the aliasaccount number may comprise a unique number associated with atransaction account number. This may further comprise deriving theplurality of base encryption keys based on the GUID master encryptionkey. The method may further comprise storing the proto-script. Theproto-script may be stored with reference to its GUID. The proto-scriptmay be stored with reference to the GUID encryption key.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and advantages of the present disclosure will become moreapparent from the detailed description set forth below when taken inconjunction with the drawings. The attached figures are illustrative ofthe systems and methods described herein.

FIG. 1 illustrates, in accordance with various embodiments, a system forrapidly provisioning contactless payment functionality to one or moremobile devices;

FIG. 2 illustrates, in accordance with various embodiments, both “push”and “pull” methods of GlobalPlatform;

FIG. 3 illustrates, in accordance with various embodiments, a processfor rapidly constructing functionality prior to a request for suchfunctionality; and

FIG. 4 illustrates, in accordance with various embodiments, a processfor rapidly provisioning functionality in response to a request for suchfunctionality.

DETAILED DESCRIPTION

The detailed description of exemplary embodiments herein makes referenceto the accompanying drawings, which show the exemplary embodiments byway of illustration and their best mode. While these exemplaryembodiments are described in sufficient detail to enable those skilledin the art to practice the disclosure, it should be understood thatother embodiments may be realized and that logical and mechanicalchanges may be made without departing from the spirit and scope of thedisclosure. Thus, the detailed description herein is presented forpurposes of illustration only and not of limitation. For example, thesteps recited in any of the method or process descriptions may beexecuted in any order and are not limited to the order presented.Moreover, any of the functions or steps may be outsourced to orperformed by one or more third parties. Furthermore, any reference tosingular includes plural embodiments, and any reference to more than onecomponent may include a singular embodiment.

A system, method and/or computer program product for rapidlyprovisioning application functionality, e.g., contactless paymentfunctionality, to one or more mobile communication devices is described.A variety of terms and acronyms, as used herein, are described and/ordefined above with respect to the background portion of this disclosureas well as, in certain instances, below.

As described herein, a variety of encryption techniques or methods maybe performed by way of any of the techniques now available in the art orwhich may become available—e.g., AES, Twofish, RSA, El Gamal, Schorrsignature, DSA, PGP, PKI, GPG (GnuPG) ECC, and symmetric and asymmetriccryptosystems. Some of these are described below.

As used herein, “perso-data” may comprise any data associated with anapplication service provider customer, such as a transaction accountcode, a transaction account spending limit, an alias account code (e.g.,a unique code associated with a transaction account code that is not thetransaction account number) and the like. Likewise, as used herein, a“perso-script” may comprise a collection of perso-data, such as a filecontaining perso-data.

To minimize the amount of real-time processing needed to support aprovisioning request, the method may comprise creating a globally uniqueidentifier (“GUID”), which can be a binary value that can be sequentialor randomly generated and a multiple of the size of the block cipherbeing used, one or more symmetric master cryptographic keys to deriveGUID specific master keys, where the derived keys can either be createdon the fly or generated and securely stored. The GUID specific masterkeys are used, as per GP, to create GUID specific base keys, eitherdirectly or by first creating a GUID specific base master key, which areused (as per GP) to create GUID specific session keys. The GUID specificsession keys are used to build the majority (e.g., approximately 95%) ofthe perso script, called the “proto-script.” The proto-scripts can bestored on the back-end systems of the entity looking to provide theapplication functionality, whether a Telco, a Service Provider, etc.During real-time activities, whether following the GP “push” or “pull”method, the remaining steps for the back-end system is to select anavailable GUID and associate it with the details of the given mobiledevice and Secure Element, such as GP Sub-Security Domain identifiers,etc. The back-end systems then use the just received/created keys (thatcorrespond to the keys on the Secure Element) to create thecorresponding session keys (as per GP) and make a portion of script thatrotates the current keys on the Secure Element to the new GUID specificbase keys. This key rotation script is pre-pended to the proto-script toyield the final perso-script that can be sent to the Secure Element forprocessing. Note that this entire approach can also work in a “batch”mode, whereby the keys could be pushed or pulled from the Secure Element(as per GP) during the manufacturing process, with the results given tothe Application Provider for finalized script building. The finalizedscripts would then be sent to the Secure Element during the real-timeprovisioning request.

With reference to FIG. 1, a system 100 for rapidly provisioningapplication functionality, e.g., contactless payment functionality, toone or more mobile communication devices is shown. The system 100 maycomprise one or more mobile communication devices 102, a Telco 104,and/or one or more backend systems 106. The one or more backend systems106 may belong to (i.e., be owned by an application service provider(“ASP”), such as American Express Travel Related Services Company).

The one or more backend systems 106 may, for example, comprise anapplication service provider (‘ASP”) comprising one or more backendsystems 106. The one or more backend systems 106 may comprise a varietyof systems, such as a “three tiered” web architecture including one ormore processors, computer-based systems, servers, storage elements,databases, and the like. In various embodiments, the backend systems 106may comprise one or more trusted service managers (“TSMs”) and/or one ormore hardware security modules (“HSMs”), each comprising a variety ofhardware and/or software. For ease of reference, any of the backendsystems 106 referred to herein may collectively and/or individually besimply referred to as a TSM.

As described above, as those of skill in the art will appreciate andwith regard to FIG. 2, GlobalPlatform provides for several encryptionmodels, such as “push” and “pull” models. With respect to the “push”model, an application service provider may request that a particularTelco 104 provide (or provision) a cryptographic key or keys (e.g., asymmetric key or keys) to a particular secure element in response, forexample, to a request by the user of the mobile communication device 102for certain contactless (e.g., payment) software and/or functionality(step 202 a). In response, the Telco 104 may follow the GP push model togenerate (e.g., randomly generate) and provide the key(s) to the secureelement (which may itself comprise a secure domain or sub-domainassociated with the ASP) on the mobile communication device 102 (step202 b). The secure element may store the key(s) (202 c), such as withinthe ASP's GP security domain. The Telco 104 may also securely provide acopy of the key to the application service provider (step 202 d). Thus,the secure element and the application service provider may share thekey(s); that is, each entity may share this key as a “shared secret.”The mobile communication device 102 (e.g., the mobile communicationdevice's security domain) may, in response to receipt of the sharedsecret, authenticate to the application service provider in preparationto receive the contactless payment software and/or functionality (step202 e).

With continuing reference to FIG. 2, an example of a “pull” model ofGlobalPlatform is shown. In general (although the pull model may beimplemented variously), the ASP may generate a public/private key pair(step 202 f). Thereupon, the ASP may provide the Telco 104, the publickey generated at step 202 f, whereupon the Telco 104 will, via GP, sendthe ASP public key to the mobile communication device 102—namely, theASP GP security domain (ASP-SD) on the mobile communication device'ssecure element (step 202 g). The ASP security domain on the mobilecommunication device 102 may thereupon randomly generate a symmetric key(i.e., a randomly generated key or “RGK”) and utilize the ASP public keyto encrypt the RGK (step 202 h). The public key may be transmitted tothe ASP via the Telco 104. The ASP may further utilize the private keyto decrypt the RGK (step 202 i). In this manner, the ASP mayauthenticate to the security domain on the mobile communication device102 using the shared keys (ENC, MAC and DEK) derived (per GP) from theRGK.

This GP “pull” approach can involve the use of public key cryptographyto resolves the vulnerability of the Telco being able to expose thecryptographic keys (shared between the Secure Element and the ServiceProvider) or the sensitive data protected by those keys (thevulnerability of the “push” method). However, even in the “pull” modelthe Service Provider or ASP may well want to rotate the keys held in theSecure Element so as to streamline cryptographic key management on theService Provider's back end systems, e.g., deriving the keys held on theSecure Element from one or more master keys using Secure Elementspecific information.

In either instance (“push” or “pull”), and with reference to FIG. 3, theapplication service provider (more particularly, the ASP's trustedservice manager or “TSM”) may, in various embodiments, securely generateand store one or more globally unique identifier (“GUID”) master keys(step 302). The TSM may (e.g., subsequently) generate GUID values (i.e.,random or deterministic values based upon any data, including perso-dataand encrypted with the GUID master keys) and/or store these GUID values(step 304). Note that the GUID acts as a surrogate for the SecureElement specific information.

Optionally, the ASP's TSM may use a GUID master key and a GUID value asderivation data to create a GUID specific Base Master Key (“BMK”), whichmay represent a “surrogate” to the RGK (step 306). In the alternative,however, step 304 may be immediately followed by step 308. Both optionsare available.

With respect to step 308, the ASP's TSM may use the GUID specific BMK(generated at step 306), the GUID master key, the GUID value, and/or anyother data suitable for derivation to create GUID specific base keys,such as an ENC key, a MAC key, and/or a DEC key (step 308).

As per GlobalPlatform, an ENC key may comprise an encryption key that isused to derive ENC session keys, and ENC session keys may protectsensitive data, such as data in commands to the chip. A MAC base key maycomprise a message authentication code key that is used to derive MACsession keys. MAC session keys provide integrity of commands and data,as well as sender authentication. A DEK key may comprise a dataencryption key (static) that protects sensitive data, such as othercryptographic keys.

Further, as per GlobalPlatform and as those of ordinary skill willappreciate, the ASP's TSM may use the GUID specific base keys (again,the ENC, MAK, DEC keys) to derive the ENC and MAC session keys and/orperhaps the DEK session key (depending upon the version of GP being usedand/or the amendment to GP being used) (step 310).

In various embodiments, the ASP's TSM may use the GUID specific ENC andMAC session keys (and in some instances the DEK base key or DEK sessionkey) to create a “proto-script.” As used herein, a proto-script maycomprise any data necessary to personalize an application (e.g.,requested functionality) to a mobile communication device 102. Such datamay include an alias account code (e.g., a unique number linked to atransaction account code) and/or payment keys (step 312). The resultantproto-script may be stored with reference(s) to its GUID and/or theidentifier to the GUID master key that was used to derive the keys thatcreated the proto-script, as described above (step 314).

With reference to FIG. 4, a process for rapidly provisioningfunctionality (e.g., contactless payment functionality) is shown. Invarious embodiments, the ASP's TSM may receive a request for application(e.g., contactless payment) functionality—however, any type offunctionality may be provisioning as described herein (402). Thisrequest may be received from mobile communication device 102 and/or abatch processor. In response to receiving such a request, the ASP's TSMmay receive the key(s) or information to derive the keys that are storedin the secure element of the mobile device 102 via the push or pullmethod (step 404). The ASP's TSM may create the ASP-SD ENC, MAC and DEKto create the ENC and MAC (and possibly DEK) session keys, as describedabove (step 406). The ASP's TSM may utilize these newly created ENC andMAC session keys, along with either the DEK or DEK session key, to builda “key rotation portion” of the perso-script that may be used to“rotate” from (or exchanges for) the original base keys stored on thesecure element in the ASP-SD of the mobile device 102 to new GUIDspecific base keys (step 408). Continuing, the ASP's TSM may pre-pendthe key rotation script to the GUID specific proto-script to finalizethe perso-script (step 410). The finalized perso-script may either betransmitted to the secure element on the mobile device 102 forprocessing (real-time) or stored for later transmission when a user of amobile communication device 102 makes a request (step 412).

In various embodiments, the secure element may process the leadingportion of the perso-script to rotate to the new GUID specific base keys(step 414). The secure element may further process the remainder of theperso-script (what was originally the proto-script) using the new GUIDspecific base keys (step 416). The secure element may further stilltransmit a status response to the ASP TSM for results of the applicationperso operation (step 418).

Therefore, although previous systems typically prevented creation of aperso-script until a request for payment functionality was received, thesystems and methods described herein permit the creation of one or moreproto-scripts far in advance of any application request. This featuremay, in turn, dramatically reduce the workload and realtime processingrequired by one or more TSMs/HSMs, as each proto-script need not becreated on the fly in response to a request for applicationfunctionality, but during, for example, periods of decreased processingrequirements, such as during nights and weekends. Accordingly, thenumber of TSMs/HSMs required by an application service provider toaccommodate millions or tens of millions of real-time requests forfunctionality may be dramatically reduced, saving the provider expenseand maintenance. Thus, functionality may be “rapidly” provisioned (incomparison to conventional systems), in that the proto-script forgeneric customers or specific to a customer may be constructed ahead ofany request for such functionality (e.g., immediately before, withinseconds before, within minutes before, within hours before, within daysbefore, within months before, within years before).

The phrases consumer, customer, user, account holder, cardmember or thelike shall include any person, entity, business, governmentorganization, business, software, hardware, machine associated with atransaction account, buys merchant offerings offered by one or moremerchants using the account and/or who is legally designated forperforming transactions on the account, regardless of whether a physicalcard is associated with the account. For example, the cardmember mayinclude a transaction account owner, an transaction account user, anaccount affiliate, a child account user, a subsidiary account user, abeneficiary of an account, a custodian of an account, and/or any otherperson or entity affiliated or associated with a transaction account. Inaddition, as used herein, a user may comprise, in various embodiments,any person who interacts and/or interfaces with a computer system (e.g.,an organizational and/or an employer computer system).

Phrases and terms similar to “transaction account” may include anyaccount that may be used to facilitate a financial transaction.

Phrases and terms similar to “financial institution” or “transactionaccount issuer” may include any entity that offers transaction accountservices. Although often referred to as a “financial institution,” thefinancial institution may represent any type of bank, lender or othertype of account issuing institution, such as credit card companies, cardsponsoring companies, or third party issuers under contract withfinancial institutions. It is further noted that other participants maybe involved in some phases of the transaction, such as an intermediarysettlement institution.

Phrases and terms similar to “business” or “merchant” may be usedinterchangeably with each other and shall mean any person, entity,distributor system, software and/or hardware that is a provider, brokerand/or any other entity in the distribution chain of goods or services.For example, a merchant may be a grocery store, a retail store, a travelagency, a service provider, an on-line merchant or the like.

As used herein, a network includes any cloud, cloud computing system orelectronic communications system or method which incorporates hardwareand/or software components. Communication among the parties may beaccomplished through any suitable communication channels, such as, forexample, a telephone network, an extranet, an intranet, Internet, pointof interaction device (point of sale device, personal digital assistant(e.g., IPHONE, PALM PILOT, BLACKBERRY), cellular phone, kiosk, etc.),online communications, satellite communications, off-linecommunications, wireless communications, transponder communications,local area network (LAN), wide area network (WAN), virtual privatenetwork (VPN), networked or linked devices, keyboard, mouse and/or anysuitable communication or data input modality. Moreover, although thesystem is frequently described herein as being implemented with TCP/IPcommunications protocols, the system may also be implemented using IPX,Appletalk, IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH),or any number of existing or future protocols. If the network is in thenature of a public network, such as the Internet, it may be advantageousto presume the network to be insecure and open to eavesdroppers.Specific information related to the protocols, standards, andapplication software utilized in connection with the Internet isgenerally known to those skilled in the art and, as such, need not bedetailed herein. See, for example, Dilip Naik, Internet Standards andProtocols (1998); Java 2 Complete, various authors, (Sybex 1999);Deborah Ray and Eric Ray, Mastering HTML 4.0 (1997); and Loshin, TCP/IPClearly Explained (1997) and David Gourley and Brian Totty, HTTP, TheDefinitive Guide (2002), the contents of which are hereby incorporatedby reference.

The various system components may be independently, separately orcollectively suitably coupled to the network via data links whichincludes, for example, a connection to an Internet Service Provider(ISP) over the local loop as is typically used in connection withstandard modem communication, cable modem, Dish networks, ISDN, DigitalSubscriber Line (DSL), or various wireless communication methods, see,e.g., Gilbert Held, Understanding Data Communications (1996), which ishereby incorporated by reference. It is noted that the network may beimplemented as other types of networks, such as an interactivetelevision (ITV) network. Moreover, the system contemplates the use,sale or distribution of any goods, services or information over anynetwork having similar functionality described herein.

“Cloud” or “Cloud computing” includes a model for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, servers, storage, applications, and services)that can be rapidly provisioned and released with minimal managementeffort or service provider interaction. Cloud computing may includelocation-independent computing, whereby shared servers provideresources, software, and data to computers and other devices on demand.For more information regarding cloud computing, see the NIST's (NationalInstitute of Standards and Technology) definition of cloud computing athttp://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf (lastvisited June 2012), which is hereby incorporated by reference in itsentirety.

A database may comprise any type of hardware and/or software (e.g., acomputer server) configured or configurable to store data and/or host adatabase. For example, database 106 may comprise a server appliancerunning a suitable server operating system (e.g., IIS) and havingdatabase software (e.g., SQL Server 2008, an Oracle database, and thelike), stored thereon. Database 106 may, in various embodiments,compress and/or analyze data, as described herein. Similarly, in variousembodiments, database may be coupled to a system for analyzing and/orcompressing data, as described herein.

Referring broadly to the attached figures, the process flows, logicalrepresentations, and/or screen shots depicted are merely embodiments andare not intended to limit the scope of the disclosure. For example, thesteps recited in any of the method or process descriptions may beexecuted in any order and may, in various embodiments, apply to thesystems as depicted. It will be appreciated that the followingdescription makes appropriate references not only to the steps depictedin the figures but also to the various system components and/or logicalrepresentations as described above.

Systems, methods and computer program products are provided. In thedetailed description herein, references to “various embodiments”, “oneembodiment”, “an embodiment”, “an example embodiment”, etc., indicatethat the embodiment described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to effect such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described. After reading the description, itwill be apparent to one skilled in the relevant art(s) how to implementthe disclosure in alternative embodiments.

Any communication, transmission and/or channel discussed herein mayinclude any system or method for delivering content (e.g. data,information, metadata, etc.), and/or the content itself. The content maybe presented in any form or medium, and in various embodiments, thecontent may be delivered electronically and/or capable of beingpresented electronically. For example, a channel may comprise a website,a uniform resource locator (“URL”), a document (e.g., a Microsoft Worddocument, a Microsoft Excel document, an Adobe .pdf document, etc.), an“ebook,” an “emagazine,” an application or microapplication (asdescribed below), an SMS or other type of text message, an email,facebook, twitter, MMS, data communication over a financial acquirernetwork, and/or other type of communication technology. In variousembodiments, a channel may be hosted or provided by a data partner.

In various embodiments, the methods described herein are implementedusing the various particular machines described herein. The methodsdescribed herein may be implemented using the below particular machines,and those hereinafter developed, in any suitable combination, as wouldbe appreciated immediately by one skilled in the art. Further, as isunambiguous from this disclosure, the methods described herein mayresult in various transformations of certain articles.

For the sake of brevity, conventional data networking, applicationdevelopment and other functional aspects of the systems (and componentsof the individual operating components of the systems) may not bedescribed in detail herein. Furthermore, the connecting lines shown inthe various figures contained herein are intended to represent exemplaryfunctional relationships and/or physical couplings between the variouselements. It should be noted that many alternative or additionalfunctional relationships or physical connections may be present in apractical system.

The various system components discussed herein may include one or moreof the following: a host server or other computing systems including aprocessor for processing digital data; a memory coupled to the processorfor storing digital data; an input digitizer coupled to the processorfor inputting digital data; an application program stored in the memoryand accessible by the processor for directing processing of digital databy the processor; a display device coupled to the processor and memoryfor displaying information derived from digital data processed by theprocessor; and a plurality of databases. Various databases used hereinmay include: user data, file system data, client data; merchant data;financial institution data; and/or like data useful in the operation ofthe system. As those skilled in the art will appreciate, user computermay include an operating system (e.g., Windows NT, Windows 95/98/2000,Windows XP, Windows Vista, Windows 7, OS2, UNIX, Linux, Solaris, MacOS,etc.) as well as various conventional support software and driverstypically associated with computers.

In various embodiments, the server may include application servers (e.g.WEB SPHERE, WEB LOGIC, JBOSS). In various embodiments, the server mayinclude web servers (e.g. APACHE, HS, GWS, SUN JAVA SYSTEM WEB SERVER).

As used herein, “transmit” may include sending electronic data from onesystem component to another over a network connection. Additionally, asused herein, “data” may include encompassing information such ascommands, queries, files, data for storage, and the like in digital orany other form.

The system contemplates uses in association with web services, utilitycomputing, pervasive and individualized computing, security and identitysolutions, autonomic computing, cloud computing, commodity computing,mobility and wireless solutions, open source, biometrics, grid computingand/or mesh computing.

Any databases discussed herein may include relational, hierarchical,graphical, or object-oriented structure and/or any other databaseconfigurations. Common database products that may be used to implementthe databases include DB2 by IBM (Armonk, N.Y.), various databaseproducts available from Oracle Corporation (e.g., MySQL) (RedwoodShores, Calif.), Microsoft Access or Microsoft SQL Server by MicrosoftCorporation (Redmond, Wash.), or any other suitable database product.Moreover, the databases may be organized in any suitable manner, forexample, as data tables or lookup tables. Each record may be a singlefile, a series of files, a linked series of data fields or any otherdata structure. Association of certain data may be accomplished throughany desired data association technique such as those known or practicedin the art. For example, the association may be accomplished eithermanually or automatically. Automatic association techniques may include,for example, a database search, a database merge, GREP, AGREP, SQL,using a key field in the tables to speed searches, sequential searchesthrough all the tables and files, sorting records in the file accordingto a known order to simplify lookup, and/or the like. The associationstep may be accomplished by a database merge function, for example,using a “key field” in pre-selected databases or data sectors. Variousdatabase tuning steps are contemplated to optimize database performance.For example, frequently used files such as indexes may be placed onseparate file systems to reduce In/Out (“I/O”) bottlenecks.

More particularly, a “key field” partitions the database according tothe high-level class of objects defined by the key field. For example,certain types of data may be designated as a key field in a plurality ofrelated data tables and the data tables may then be linked on the basisof the type of data in the key field. The data corresponding to the keyfield in each of the linked data tables is preferably the same or of thesame type. However, data tables having similar, though not identical,data in the key fields may also be linked by using AGREP, for example.In accordance with one embodiment, any suitable data storage techniquemay be utilized to store data without a standard format. Data sets maybe stored using any suitable technique, including, for example, storingindividual files using an ISO/IEC 7816-4 file structure; implementing adomain whereby a dedicated file is selected that exposes one or moreelementary files containing one or more data sets; using data setsstored in individual files using a hierarchical filing system; data setsstored as records in a single file (including compression, SQLaccessible, hashed via one or more keys, numeric, alphabetical by firsttuple, etc.); Binary Large Object (BLOB); stored as ungrouped dataelements encoded using ISO/IEC 7816-6 data elements; stored as ungroupeddata elements encoded using ISO/IEC Abstract Syntax Notation (ASN.1) asin ISO/IEC 8824 and 8825; and/or other proprietary techniques that mayinclude fractal compression methods, image compression methods, etc.

In one exemplary embodiment, the ability to store a wide variety ofinformation in different formats is facilitated by storing theinformation as a BLOB. Thus, any binary information can be stored in astorage space associated with a data set. As discussed above, the binaryinformation may be stored on the financial transaction instrument orexternal to but affiliated with the financial transaction instrument.The BLOB method may store data sets as ungrouped data elements formattedas a block of binary via a fixed memory offset using either fixedstorage allocation, circular queue techniques, or best practices withrespect to memory management (e.g., paged memory, least recently used,etc.). By using BLOB methods, the ability to store various data setsthat have different formats facilitates the storage of data associatedwith the financial transaction instrument by multiple and unrelatedowners of the data sets. For example, a first data set which may bestored may be provided by a first party, a second data set which may bestored may be provided by an unrelated second party, and yet a thirddata set which may be stored, may be provided by an third partyunrelated to the first and second party. Each of these three exemplarydata sets may contain different information that is stored usingdifferent data storage formats and/or techniques. Further, each data setmay contain subsets of data that also may be distinct from othersubsets.

As stated above, in various embodiments, the data can be stored withoutregard to a common format. However, in one exemplary embodiment, thedata set (e.g., BLOB) may be annotated in a standard manner whenprovided for manipulating the data onto the financial transactioninstrument. The annotation may comprise a short header, trailer, orother appropriate indicator related to each data set that is configuredto convey information useful in managing the various data sets. Forexample, the annotation may be called a “condition header”, “header”,“trailer”, or “status”, herein, and may comprise an indication of thestatus of the data set or may include an identifier correlated to aspecific issuer or owner of the data. In one example, the first threebytes of each data set BLOB may be configured or configurable toindicate the status of that particular data set; e.g., LOADED,INITIALIZED, READY, BLOCKED, REMOVABLE, or DELETED. Subsequent bytes ofdata may be used to indicate for example, the identity of the issuer,user, transaction/membership account identifier or the like. Each ofthese condition annotations are further discussed herein.

The data set annotation may also be used for other types of statusinformation as well as various other purposes. For example, the data setannotation may include security information establishing access levels.The access levels may, for example, be configured to permit or monitoronly certain individuals, levels of employees, companies, or otherentities accessing data sets, or to permit or monitor access to specificdata sets based on the transaction, merchant, issuer, user or the like.Furthermore, the security information may restrict, permit, and/ormonitor only certain actions such as accessing, modifying, and/ordeleting data sets. In one example, the data set annotation may indicateor track that only the data set owner or the user are permitted todelete a data set, various identified users may be permitted to accessthe data set for reading, and others are altogether excluded fromaccessing the data set. However, other access restriction or monitoringmay also be used which may allow various entities to access a data setwith various permission levels as appropriate, and/or which monitoringmay also be used to track various entities (e.g., users or systems)accessing a data set with various permission levels. Thus, in variousembodiments, tracking information may enable a system administrator toinquire into one or more user activities, which inquiry may permit thesystem administrator to adjust one or more access controls, modify oneor more user groups or transaction clusters, and the like.

The data, including the header or trailer may be received by a standalone interaction device configured to add, delete, modify, or augmentthe data in accordance with the header or trailer. As such, in oneembodiment, the header or trailer is not stored on the transactiondevice along with the associated issuer-owned data but instead theappropriate action may be taken by providing to the transactioninstrument user at the stand alone device, the appropriate option forthe action to be taken. The system may contemplate a data storagearrangement wherein the header or trailer, or header or trailer history,of the data is stored on the transaction instrument in relation to theappropriate data.

One skilled in the art will also appreciate that, for security reasons,any databases, systems, devices, servers or other components of thesystem may consist of any combination thereof at a single location or atmultiple locations, wherein each database or system includes any ofvarious suitable security features, such as firewalls, access codes,encryption, decryption, compression, decompression, and/or the like.

A firewall may include any hardware and/or software suitably configuredto protect CMS components and/or enterprise computing resources fromusers of other networks. Further, a firewall may be configured to limitor restrict access to various systems and components behind the firewallfor web clients connecting through a web server. Firewall may reside invarying configurations including Stateful Inspection, Proxy based,access control lists, and Packet Filtering among others. Firewall may beintegrated within an web server or any other CMS components or mayfurther reside as a separate entity. A firewall may implement networkaddress translation (“NAT”) and/or network address port translation(“NAPT”). A firewall may accommodate various tunneling protocols tofacilitate secure communications, such as those used in virtual privatenetworking. A firewall may implement a demilitarized zone (“DMZ”) tofacilitate communications with a public network such as the Internet. Afirewall may be integrated as software within an Internet server, anyother application server components or may reside within anothercomputing device or may take the form of a standalone hardwarecomponent.

The computers discussed herein may provide a suitable website or otherInternet-based graphical user interface which is accessible by users. Inone embodiment, the Microsoft Internet Information Server (IIS),Microsoft Transaction Server (MTS), and Microsoft SQL Server, are usedin conjunction with the Microsoft operating system, Microsoft NT webserver software, a Microsoft SQL Server database system, and a MicrosoftCommerce Server. Additionally, components such as Access or MicrosoftSQL Server, Oracle, Sybase, Informix MySQL, Interbase, etc., may be usedto provide an Active Data Object (ADO) compliant database managementsystem. In one embodiment, the Apache web server is used in conjunctionwith a Linux operating system, a MySQL database, and the Perl, PHP,and/or Python programming languages.

Any of the communications, inputs, storage, databases or displaysdiscussed herein may be facilitated through a website having web pages.The term “web page” as it is used herein is not meant to limit the typeof documents and applications that might be used to interact with theuser. For example, a typical website might include, in addition tostandard HTML documents, various forms, Java applets, JavaScript, activeserver pages (ASP), common gateway interface scripts (CGI), extensiblemarkup language (XML), dynamic HTML, cascading style sheets (CSS), AJAX(Asynchronous Javascript And XML), helper applications, plug-ins, andthe like. A server may include a web service that receives a requestfrom a web server, the request including a URL(http://yahoo.com/stockquotes/ge) and an IP address (123.56.789.234).The web server retrieves the appropriate web pages and sends the data orapplications for the web pages to the IP address. Web services areapplications that are capable of interacting with other applicationsover a communications means, such as the internet. Web services aretypically based on standards or protocols such as XML, SOAP, AJAX, WSDLand UDDI. Web services methods are well known in the art, and arecovered in many standard texts. See, e.g., Alex Nghiem, IT Web Services:A Roadmap for the Enterprise (2003), hereby incorporated by reference.

Middleware may include any hardware and/or software suitably configuredto facilitate communications and/or process transactions betweendisparate computing systems. Middleware components are commerciallyavailable and known in the art. Middleware may be implemented throughcommercially available hardware and/or software, through custom hardwareand/or software components, or through a combination thereof. Middlewaremay reside in a variety of configurations and may exist as a standalonesystem or may be a software component residing on the Internet server.Middleware may be configured to process transactions between the variouscomponents of an application server and any number of internal orexternal systems for any of the purposes disclosed herein. WebSphere MQ™(formerly MQSeries) by IBM, Inc. (Armonk, N.Y.) is an example of acommercially available middleware product. An Enterprise Service Bus(“ESB”) application is another example of middleware.

Practitioners will also appreciate that there are a number of methodsfor displaying data within a browser-based document. Data may berepresented as standard text or within a fixed list, scrollable list,drop-down list, editable text field, fixed text field, pop-up window,and the like. Likewise, there are a number of methods available formodifying data in a web page such as, for example, free text entry usinga keyboard, selection of menu items, check boxes, option boxes, and thelike.

The system and method may be described herein in terms of functionalblock components, screen shots, optional selections and variousprocessing steps. It should be appreciated that such functional blocksmay be realized by any number of hardware and/or software componentsconfigured to perform the specified functions. For example, the systemmay employ various integrated circuit components, e.g., memory elements,processing elements, logic elements, look-up tables, and the like, whichmay carry out a variety of functions under the control of one or moremicroprocessors or other control devices. Similarly, the softwareelements of the system may be implemented with any programming orscripting language such as C, C++, C#, Java, JavaScript, VBScript,Macromedia Cold Fusion, COBOL, Microsoft Active Server Pages, assembly,PERL, PHP, awk, Python, Visual Basic, SQL Stored Procedures, PL/SQL, anyUNIX shell script, and extensible markup language (XML) with the variousalgorithms being implemented with any combination of data structures,objects, processes, routines or other programming elements. Further, itshould be noted that the system may employ any number of conventionaltechniques for data transmission, signaling, data processing, networkcontrol, and the like. Still further, the system could be used to detector prevent security issues with a client-side scripting language, suchas JavaScript, VB Script or the like. For a basic introduction ofcryptography and network security, see any of the following references:(1) “Applied Cryptography: Protocols, Algorithms, And Source Code In C,”by Bruce Schneier, published by John Wiley & Sons (second edition,1995); (2) “Java Cryptography” by Jonathan Knudson, published byO'Reilly & Associates (1998); (3) “Cryptography & Network Security:Principles & Practice” by William Stallings, published by Prentice Hall;all of which are hereby incorporated by reference.

Each participant is equipped with a computing device in order tointeract with the system and facilitate online commerce transactions.The customer has a computing unit in the form of a personal computer,although other types of computing units may be used including laptops,notebooks, hand held computers, set-top boxes, cellular or mobiletelephones, touch-tone telephones and the like. The merchant has acomputing unit implemented in the form of a computer-server, althoughother implementations are contemplated by the system. The bank has acomputing center shown as a main frame computer. However, the bankcomputing center may be implemented in other forms, such as amini-computer, a PC server, a network of computers located in the sameof different geographic locations, or the like. Moreover, the systemcontemplates the use, sale or distribution of any goods, services orinformation over any network having similar functionality describedherein

The merchant computer and the bank computer may be interconnected via asecond network, referred to as a payment network. The payment networkwhich may be part of certain transactions represents existingproprietary networks that presently accommodate transactions for creditcards, debit cards, and other types of financial/banking cards. Thepayment network is a closed network that is assumed to be secure fromeavesdroppers. Exemplary transaction networks may include the AMERICANEXPRESS, VISANET and the VERIPHONE networks.

The electronic commerce system may be implemented at the customer andissuing bank. In an exemplary implementation, the electronic commercesystem is implemented as computer software modules loaded onto thecustomer computer and the banking computing center. The merchantcomputer does not require any additional software to participate in theonline commerce transactions supported by the online commerce system.

As will be appreciated by one of ordinary skill in the art, the systemmay be embodied as a customization of an existing system, an add-onproduct, a processing apparatus executing upgraded software, astand-alone system, a distributed system, a method, a data processingsystem, a device for data processing, and/or a computer program product.Accordingly, any portion of the system or a module may take the form ofa processing apparatus executing code, an internet based embodiment, anentirely hardware embodiment, or an embodiment combining aspects of theinternet, software and hardware. Furthermore, the system may take theform of a computer program product on a computer-readable storage mediumhaving computer-readable program code means embodied in the storagemedium. Any suitable computer-readable storage medium may be utilized,including hard disks, CD-ROM, optical storage devices, magnetic storagedevices, and/or the like.

The system and method is described herein with reference to screenshots, block diagrams and flowchart illustrations of methods, apparatus(e.g., systems), and computer program products according to variousembodiments. It will be understood that each functional block of theblock diagrams and the flowchart illustrations, and combinations offunctional blocks in the block diagrams and flowchart illustrations,respectively, can be implemented by computer program instructions.

These computer program instructions may be loaded onto a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructionsthat execute on the computer or other programmable data processingapparatus create means for implementing the functions specified in theflowchart block or blocks. These computer program instructions may alsobe stored in a computer-readable memory that can direct a computer orother programmable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function specified in the flowchart block or blocks.The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Accordingly, functional blocks of the block diagrams and flowchartillustrations support combinations of means for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instruction means for performing the specified functions. Itwill also be understood that each functional block of the block diagramsand flowchart illustrations, and combinations of functional blocks inthe block diagrams and flowchart illustrations, can be implemented byeither special purpose hardware-based computer systems which perform thespecified functions or steps, or suitable combinations of specialpurpose hardware and computer instructions. Further, illustrations ofthe process flows and the descriptions thereof may make reference touser windows, webpages, websites, web forms, prompts, etc. Practitionerswill appreciate that the illustrated steps described herein may comprisein any number of configurations including the use of windows, webpages,web forms, popup windows, prompts and the like. It should be furtherappreciated that the multiple steps as illustrated and described may becombined into single webpages and/or windows but have been expanded forthe sake of simplicity. In other cases, steps illustrated and describedas single process steps may be separated into multiple webpages and/orwindows but have been combined for simplicity.

The term “non-transitory” is to be understood to remove only propagatingtransitory signals per se from the claim scope and does not relinquishrights to all standard computer-readable media that are not onlypropagating transitory signals per se. Stated another way, the meaningof the term “non-transitory computer-readable medium” and“non-transitory computer-readable storage medium” should be construed toexclude only those types of transitory computer-readable media whichwere found in In Re Nuijten to fall outside the scope of patentablesubject matter under 35 U.S.C. §101.

Benefits, other advantages, and solutions to problems have beendescribed herein with regard to specific embodiments. However, thebenefits, advantages, solutions to problems, and any elements that maycause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as critical, required, or essentialfeatures or elements of the disclosure. The scope of the disclosure isaccordingly to be limited by nothing other than the appended claims, inwhich reference to an element in the singular is not intended to mean“one and only one” unless explicitly so stated, but rather “one ormore.” Moreover, where a phrase similar to ‘at least one of A, B, and C’or ‘at least one of A, B, or C’ is used in the claims or specification,it is intended that the phrase be interpreted to mean that A alone maybe present in an embodiment, B alone may be present in an embodiment, Calone may be present in an embodiment, or that any combination of theelements A, B and C may be present in a single embodiment; for example,A and B, A and C, B and C, or A and B and C. Although the disclosureincludes a method, it is contemplated that it may be embodied ascomputer program instructions on a tangible computer-readable carrier,such as a magnetic or optical memory or a magnetic or optical disk. Allstructural, chemical, and functional equivalents to the elements of theabove-described exemplary embodiments that are known to those ofordinary skill in the art are expressly incorporated herein by referenceand are intended to be encompassed by the present claims. Moreover, itis not necessary for a device or method to address each and everyproblem sought to be solved by the present disclosure, for it to beencompassed by the present claims. Furthermore, no element, component,or method step in the present disclosure is intended to be dedicated tothe public regardless of whether the element, component, or method stepis explicitly recited in the claims. No claim element herein is to beconstrued under the provisions of 35 U.S.C. 112(f) unless the element isexpressly recited using the phrase “means for.” As used herein, theterms “comprises”, “comprising”, or any other variation thereof, areintended to cover a non-exclusive inclusion, such that a process,method, article, or apparatus that comprises a list of elements does notinclude only those elements but may include other elements not expresslylisted or inherent to such process, method, article, or apparatus.

Phrases and terms similar to “account”, “account number”, “account code”or “consumer account” as used herein, may include any device, code(e.g., one or more of an authorization/access code, personalidentification number (“PIN”), Internet code, other identification code,and/or the like), number, letter, symbol, digital certificate, smartchip, digital signal, analog signal, biometric or otheridentifier/indicia suitably configured to allow the consumer to access,interact with or communicate with the system. The account number mayoptionally be located on or associated with a rewards account, chargeaccount, credit account, debit account, prepaid account, telephone card,embossed card, smart card, magnetic stripe card, bar code card,transponder, radio frequency card or an associated account.

The system may include or interface with any of the foregoing accounts,devices, and/or a transponder and reader (e.g. RFID reader) in RFcommunication with the transponder (which may include a fob), orcommunications between an initiator and a target enabled by near fieldcommunications (NFC). Typical devices may include, for example, a keyring, tag, card, cell or mobile phone, wristwatch or any such formcapable of being presented for interrogation. Moreover, the system,computing unit or device discussed herein may include a “pervasivecomputing device,” which may include a traditionally non-computerizeddevice that is embedded with a computing unit. Examples may includewatches, Internet enabled kitchen appliances, restaurant tables embeddedwith RF readers, wallets or purses with imbedded transponders, etc.Furthermore, a device or financial transaction instrument may haveelectronic and communications functionality enabled, for example, by: anetwork of electronic circuitry that is printed or otherwiseincorporated onto or within the transaction instrument (and typicallyreferred to as a “smart card”); a fob having a transponder and an RFIDreader; and/or near field communication (NFC) technologies. For moreinformation regarding NFC, refer to the following specifications all ofwhich are incorporated by reference herein: ISO/IEC 18092/ECMA-340, ISO14443, Near Field Communication Interface and Protocol-1 (NFCIP-1);ISO/IEC 21481/ECMA-352, Near Field Communication Interface andProtocol-2 (NFCIP-2); and EMV 4.2 available athttp://www.emvco.com/default.aspx.

The account number may be distributed and stored in any form of plastic,electronic, magnetic, radio frequency, wireless, audio and/or opticaldevice capable of transmitting or downloading data from itself to asecond device. A consumer account number may be, for example, asixteen-digit account number, although each credit provider has its ownnumbering system, such as the fifteen-digit numbering system used byAmerican Express. Each company's account numbers comply with thatcompany's standardized format such that the company using afifteen-digit format will generally use three-spaced sets of numbers, asrepresented by the number “0000 000000 00000”. The first five to sevendigits are reserved for processing purposes and identify the issuingbank, account type, etc. In this example, the last (fifteenth) digit isused as a sum check for the fifteen digit number. The intermediaryeight-to-eleven digits are used to uniquely identify the consumer. Amerchant account number may be, for example, any number or alpha-numericcharacters that identify a particular merchant for purposes of accountacceptance, account reconciliation, reporting, or the like.

In various embodiments, an account number may identify a consumer. Inaddition, in various embodiments, a consumer may be identified by avariety of identifiers, including, for example, an email address, atelephone number, a cookie id, a radio frequency identifier (RFID), abiometric, and the like.

The terms “payment vehicle,” “financial transaction instrument,”“transaction instrument” and/or the plural form of these terms may beused interchangeably throughout to refer to a financial instrument.

Phrases and terms similar to “internal data” or “perso-data” may includeany data a credit issuer possesses or acquires pertaining to aparticular consumer. Internal data may be gathered before, during, orafter a relationship between the credit issuer and the transactionaccount holder (e.g., the consumer or buyer). Such data may includeconsumer demographic data. Consumer demographic data includes any datapertaining to a consumer. Consumer demographic data may include, forexample, consumer name, address, telephone number, email address,employer and social security number. Consumer transactional data is anydata pertaining to the particular transactions in which a consumerengages during any given time period. Consumer transactional data mayinclude, for example, transaction amount, transaction time, transactionvendor/merchant, and transaction vendor/merchant location. Transactionvendor/merchant location may contain a high degree of specificity to avendor/merchant. For example, transaction vendor/merchant location mayinclude a particular gasoline filing station in a particular postal codelocated at a particular cross section or address. Also, for example,transaction vendor/merchant location may include a particular webaddress, such as a Uniform Resource Locator (“URL”), an email addressand/or an Internet Protocol (“IP”) address for a vendor/merchant.Transaction vendor/merchant, and transaction vendor/merchant locationmay be associated with a particular consumer and further associated withsets of consumers. Consumer payment data includes any data pertaining toa consumer's history of paying debt obligations. Consumer payment datamay include consumer payment dates, payment amounts, balance amount, andcredit limit. Internal data may further comprise records of consumerservice calls, complaints, requests for credit line increases,questions, and comments. A record of a consumer service call includes,for example, date of call, reason for call, and any transcript orsummary of the actual call.

Phrases similar to a “payment processor” may include a company (e.g., athird party) appointed (e.g., by a merchant) to handle transactions. Apayment processor may include an issuer, acquirer, authorizer and/or anyother system or entity involved in the transaction process. Paymentprocessors may be broken down into two types: front-end and back-end.Front-end payment processors have connections to various transactionaccounts and supply authorization and settlement services to themerchant banks' merchants. Back-end payment processors acceptsettlements from front-end payment processors and, via The FederalReserve Bank, move money from an issuing bank to the merchant bank. Inan operation that will usually take a few seconds, the payment processorwill both check the details received by forwarding the details to therespective account's issuing bank or card association for verification,and may carry out a series of anti-fraud measures against thetransaction. Additional parameters, including the account's country ofissue and its previous payment history, may be used to gauge theprobability of the transaction being approved. In response to thepayment processor receiving confirmation that the transaction accountdetails have been verified, the information may be relayed back to themerchant, who will then complete the payment transaction. In response tothe verification being denied, the payment processor relays theinformation to the merchant, who may then decline the transaction.Phrases similar to a “payment gateway” or “gateway” may include anapplication service provider service that authorizes payments fore-businesses, online retailers, and/or traditional brick and mortarmerchants. The gateway may be the equivalent of a physical point of saleterminal located in most retail outlets. A payment gateway may protecttransaction account details by encrypting sensitive information, such astransaction account numbers, to ensure that information passes securelybetween the customer and the merchant and also between merchant andpayment processor.

What is claimed is:
 1. A method comprising: generating, by aprovisioning computer-based system and prior to a request forprovisioning contactless payment functionality, a GUID (globally uniqueidentifier) master encryption key, wherein the GUID comprises a uniqueidentifier that is associated with a transaction account customer;deriving, by the computer-based system and based on a GUID value andprior to the request for provisioning contactless payment functionality,a GUID specific base master encryption key associated with a GUID value,wherein the GUID specific base master encryption key is based on theGUID value and the GUID master encryption key; deriving, by thecomputer-based system and using a symmetric master cryptographic key andprior to the request for provisioning contactless payment functionality,a GUID specific base master key; creating, by the computer-based systemand using the GUID specific base master key and prior to the request forprovisioning contactless payment functionality, a GUID specific basekey; creating, by the computer-based system and using the GUID specificbase master key, a GUID specific base session key; creating, by thecomputer-based system and using the GUID specific base session key andprior to the request for provisioning contactless payment functionality,a majority of a perso-script that forms the proto-script, creating, bythe computer-based system and after the request for provisioningcontactless payment functionality, an additional portion of theperso-script prepended to the proto-script to rotate from one or morebase encryption keys stored on a secure element to the GUID specificbase key; wherein the portion of the perso-script comprises a filehaving perso-data associated with details of a mobile device and asecure element associated with the transaction account customer; andsending, by the computer-based system and after the request forprovisioning contactless payment functionality, the perso-script to thesecure element for processing, which executes the prepended portion ofthe perso-script to rotate to GUID specific base key and then completesthe perso-script that is protected under the GUID specific base sessionkey to complete the perso-script.
 2. The method of claim 1, wherein theone or more base encryption keys comprise ENC and MAC base keys.
 3. Themethod of claim 1, wherein the perso-data comprises an alias accountnumber, the alias account number comprising a unique number associatedwith a transaction account number.
 4. The method of claim 1, furthercomprising storing, by the computer-based system, the proto-script. 5.The method of claim 1, wherein the proto-script is stored with referenceto its GUID.
 6. The method of claim 1, wherein the proto-script isstored with reference to the GUID encryption key.
 7. An article ofmanufacture including a non-transitory, tangible computer readablestorage medium having instructions stored thereon that, in response toexecution by a provisioning computer-based system, cause thecomputer-based system to perform operations comprising: generating, bythe computer-based system and prior to a request for provisioningcontactless payment functionality, a GUID (globally unique identifier)master encryption key, wherein the GUID comprises a unique identifierthat is associated with a transaction account customer; deriving, by thecomputer-based system and based on a GUID value and prior to the requestfor provisioning contactless payment functionality, a GUID specific basemaster encryption key associated with a GUID value, wherein the GUIDspecific base master encryption key is based on the GUID value and theGUID master encryption key; deriving, by the computer-based system andusing a symmetric master cryptographic key and prior to the request forprovisioning contactless payment functionality, a GUID specific basemaster key; creating, by the computer-based system and using the GUIDspecific base master key and prior to the request for provisioningcontactless payment functionality, a GUID specific base key; creating,by the computer-based system and using the GUID specific base masterkey, a GUID specific base session key; creating, by the computer-basedsystem and using the GUID specific base session key and prior to therequest for provisioning contactless payment functionality, a majorityof a perso-script that forms the proto-script, creating, by thecomputer-based system and after the request for provisioning contactlesspayment functionality, an additional portion of the perso-scriptprepended to the proto-script to rotate from one or more base encryptionkeys stored on a secure element to the GUID specific base key; whereinthe portion of the perso-script comprises a file having perso-dataassociated with details of a mobile device and a secure elementassociated with the transaction account customer; and sending, by thecomputer-based system and after the request for provisioning contactlesspayment functionality, the perso-script to the secure element forprocessing, which executes the prepended portion of the perso-script torotate to GUID specific base key and then completes the perso-scriptthat is protected under the GUID specific base session key.
 8. Thearticle of claim 7, wherein the perso-data comprises an alias accountnumber, the alias account number comprising a unique number associatedwith a transaction account number.
 9. The article of claim 7, furthercomprising storing, by the computer-based system, the proto-script. 10.The article of claim 7, wherein the proto-script is stored withreference to its GUID.
 11. A system comprising: a provisioningprocessor, a tangible, non-transitory memory configured to communicatewith the processor, the tangible, non-transitory memory havinginstructions stored thereon that, in response to execution by theprocessor, cause the processor to perform operations comprising:generating, by the processor and prior to a request for provisioningcontactless payment functionality, a GUID (globally unique identifier)master encryption key, wherein the GUID comprises a unique identifierthat is associated with a transaction account customer; deriving, by theprocessor and based on a GUID value and prior to the request forprovisioning contactless payment functionality, a GUID specific basemaster encryption key associated with a GUID value, wherein the GUIDspecific base master encryption key is based on the GUID value and theGUID master encryption key; deriving, by the processor and using asymmetric master cryptographic key and prior to the request forprovisioning contactless payment functionality, a GUID specific basemaster key; creating, by the processor and using the GUID specific basemaster key and prior to the request for provisioning contactless paymentfunctionality, a GUID specific base key; creating, by the processor andusing the GUID specific base master key, a GUID specific base sessionkey; creating, by the processor and using the GUID specific base sessionkey and prior to the request for provisioning contactless paymentfunctionality, a majority of a perso-script that forms the proto-script,creating, by the processor and after the request for provisioningcontactless payment functionality, an additional portion of theperso-script prepended to the proto-script to rotate from one or morebase encryption keys stored on a secure element to the GUID specificbase key; wherein the portion of the perso-script comprises a filehaving perso-data associated with details of a mobile device and asecure element associated with the transaction account customer; andsending, by the processor and after the request for provisioningcontactless payment functionality, the perso-script to the secureelement for processing, which executes the prepended portion of theperso-script to rotate to GUID specific base key and then completes theperso-script that is protected under the GUID specific base session key.12. The system of claim 11, wherein the perso-data comprises an aliasaccount number, the alias account number comprising a unique numberassociated with a transaction account number.
 13. The system of claim11, further comprising storing, by the processor, the proto-script. 14.The system of claim 11, wherein the proto-script is stored withreference to its GUID.
 15. The method of claim 1, wherein the sendingoccurs in at least one of batch processing or real-time.